home *** CD-ROM | disk | FTP | other *** search
PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) NNNNAAAAMMMMEEEE ppppmmmmllllooooggggggggeeeerrrr - create archive log for performance metrics SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS $$$$PPPPCCCCPPPP____BBBBIIIINNNNAAAADDDDMMMM____DDDDIIIIRRRR////ppppmmmmllllooooggggggggeeeerrrr [----cccc _c_o_n_f_i_g_f_i_l_e] [----hhhh _h_o_s_t] [----llll _l_o_g_f_i_l_e] [----LLLL] [----nnnn _p_m_n_s_f_i_l_e] [----PPPP] [----rrrr] [----ssss _e_n_d_s_i_z_e] [----tttt _i_n_t_e_r_v_a_l] [----TTTT _e_n_d_t_i_m_e] [----vvvv _v_o_l_s_i_z_e] [----VVVV _v_e_r_s_i_o_n] [----xxxx _f_d] _a_r_c_h_i_v_e DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN ppppmmmmllllooooggggggggeeeerrrr creates the archive logs of performance metric values that may be ``played back'' by other Performance Co-Pilot (see PPPPCCCCPPPPIIIInnnnttttrrrroooo(1)) tools. These logs form the basis of the VCR paradigm and retrospective performance analysis services common to the PCP toolkit. The mandatory argument _a_r_c_h_i_v_e is the base name for the physical files that constitute an archive log. The ----VVVV option specifies whether a version 1 or version 2 archive is generated. A version 2 archive also stores the associated Performance Metrics Name Space (PMNS). By default a version 2 archive is generated. Unless directed to another host by the ----hhhh option, ppppmmmmllllooooggggggggeeeerrrr will contact the Performance Metrics Collector Daemon (PMCD) on the local host and use that as the source of the metric values to be logged. To support the required flexibility and control over what is logged and when, ppppmmmmllllooooggggggggeeeerrrr maintains an independent two level logging state for each instance of each performance metric. At the first (mandatory) level, logging is allowed to be oooonnnn (with an associated interval between samples), or ooooffffffff or mmmmaaaayyyybbbbeeee. In the latter case, the second (advisory) level logging is allowed to be oooonnnn (with an associated interval between samples), or ooooffffffff. The mandatory level allows universal specification that some metrics must be logged, or must nnnnooootttt be logged. The default state for all instances of all metrics when ppppmmmmllllooooggggggggeeeerrrr starts is mandatory maybe and advisory off. Use ppppmmmmllllcccc(1) to interrogate and change the logging state once ppppmmmmllllooooggggggggeeeerrrr is running. If a metric's state is mandatory (on or off) and a request is made to change it to mandatory maybe, the new state is mandatory maybe and advisory off. If a metric's state is already advisory (on or off) and a request is made to change it to mandatory maybe, the current state is retained. It is not possible for ppppmmmmllllooooggggggggeeeerrrr to log specific instances of a metric and all instances of the same metric concurrently. If specific instances are being logged and a request to log all instances is made, then all instances of the metric will be logged according to the new request, superseding any prior logging request for the metric. A request to log all instances of a metric will supersede any previous request to log all PPPPaaaaggggeeee 1111 PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) instances. A request to log specific instances of a metric when all instances are already being logged is refused. To do this one must turn off logging for all instances of the metric first. In each case, the validity of the request is checked first; for example a request to change a metric's logging state to advisory on when it is currently mandatory off is never permitted (it is necessary to change the state to mandatory maybe first). Optionally, each system running ppppmmmmccccdddd(1) may also be configured to run a ``primary'' ppppmmmmllllooooggggggggeeeerrrr instance. Like ppppmmmmccccdddd(1), this ppppmmmmllllooooggggggggeeeerrrr instance is launched by $$$$PPPPCCCCPPPP____RRRRCCCC____DDDDIIIIRRRR////ppppccccpppp. On Irix the launch is affected by the files /_e_t_c/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r (use cccchhhhkkkkccccoooonnnnffffiiiigggg(1M) to activate or disable the primary ppppmmmmllllooooggggggggeeeerrrr instance), /_e_t_c/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r._o_p_t_i_o_n_s (command line options passed to the primary ppppmmmmllllooooggggggggeeeerrrr). $_P_C_P__V_A_R__D_I_R/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r/_c_o_n_f_i_g._d_e_f_a_u_l_t is the default initial configuration file for the primary ppppmmmmllllooooggggggggeeeerrrr. The primary ppppmmmmllllooooggggggggeeeerrrr instance is identified by the ----PPPP option. There may be at most one ``primary'' ppppmmmmllllooooggggggggeeeerrrr instance on each system with an active ppppmmmmccccdddd(1). The primary ppppmmmmllllooooggggggggeeeerrrr instance (if any) must be running on the same host as the ppppmmmmccccdddd(1) to which it connects, so the ----hhhh and ----PPPP options are mutually exclusive. When launched as a non-primary instance, ppppmmmmllllooooggggggggeeeerrrr will exit immediately if the configuration file causes no metric logging to be scheduled. The ----LLLL option overrides this behavior, and causes a non-primary ppppmmmmllllooooggggggggeeeerrrr instance to ``linger'', presumably pending some future dynamic re- configuration and state change via ppppmmmmllllcccc(1). ppppmmmmllllooooggggggggeeeerrrr will also linger without the ----LLLL option being used if all the metrics to be logged are logged as once only metrics. When the once only metrics have been logged, a warning message will be generated stating that the event queue is empty and no more events will be scheduled. By default all diagnostics and errors from ppppmmmmllllooooggggggggeeeerrrr are written to the file _p_m_l_o_g_g_e_r._l_o_g in the directory where ppppmmmmllllooooggggggggeeeerrrr is launched. The ----llll option may be used to override the default behavior. If the log file cannot be created or is not writable, output is written to standard error instead. If specified, the ----ssss option instructs ppppmmmmllllooooggggggggeeeerrrr to terminate after a certain size in records, bytes or time units has been accumulated. If _e_n_d_s_i_z_e is an integer then _e_n_d_s_i_z_e records will be written to the log. If _e_n_d_s_i_z_e is suffixed by bbbb or bbbbyyyytttteeeessss then _e_n_d_s_i_z_e bytes of the archive data will be written out (note, however, that archive log record boundaries will not be broken and so this limit may be slightly surpassed). Other viable file size units include: KKKK, KKKKbbbb, KKKKiiiilllloooobbbbyyyytttteeee for kilobytes and MMMM, MMMMbbbb, MMMMeeeeggggaaaabbbbyyyytttteeee for megabytes. These units may be optionally suffixed by an ssss and may be of mixed case. Alternatively _e_n_d_s_i_z_e may be suffixed using a time unit as described in PPPPCCCCPPPPIIIInnnnttttrrrroooo(1) for the _i_n_t_e_r_v_a_l argument (to the standard PCP tool option ----tttt). Some examples of different formats: ----ssss 111100000000 PPPPaaaaggggeeee 2222 PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) ----ssss 111100000000bbbbyyyytttteeeessss ----ssss 111100000000KKKK ----ssss 111100000000MMMMbbbb ----ssss 11110000mmmmiiiinnnnssss ----ssss 11110000hhhhoooouuuurrrrssss The default is for ppppmmmmllllooooggggggggeeeerrrr to run forever. The ----rrrr option causes the size of the physical record(s) for each group of metrics and the expected contribution of the group to the size of the PCP archive for one full day of collection to be reported in the log file. This information is reported the first time each group is successfully written to the archive. The log file is potentially a multi-volume data set, and the ----vvvv option causes ppppmmmmllllooooggggggggeeeerrrr to start a new volume after a certain size in records, bytes, or time units has been accumulated for the current volume. The format of this size specification is identical to that of the ----ssss option (see above). The default is for ppppmmmmllllooooggggggggeeeerrrr to create a single volume log. Additional volume switches can also be forced asynchronously by either using ppppmmmmllllcccc(1) or sending ppppmmmmllllooooggggggggeeeerrrr a SIGHUP signal (see below). Note, if a scheduled volume switch is in operation due to the ----vvvv option, then its counters will be reset after an asynchronous switch. Normally ppppmmmmllllooooggggggggeeeerrrr operates on the distributed Performance Metrics Name Space (PMNS), however if the ----nnnn option is specified an alternative local PMNS is loaded from the file _p_m_n_s_f_i_l_e. Under normal circumstances, ppppmmmmllllooooggggggggeeeerrrr will run forever (except for a ----ssss option or a termination signal). The ----TTTT option may be used to limit the execution time using the format of time as prescribed by PPPPCCCCPPPPIIIInnnnttttrrrroooo(1). Some examples of different formats: ----TTTT 11110000mmmmiiiinnnnssss ----TTTT ''''@@@@ 11111111::::33330000'''' From this it can be seen that ----TTTT 11110000mmmmiiiinnnnssss and ----ssss 11110000mmmmiiiinnnnssss perform identical actions. When ppppmmmmllllooooggggggggeeeerrrr receives a SIGHUP signal, the current volume of the log is closed, and a new volume is opened. This mechanism (or the alternative mechanism via ppppmmmmllllcccc(1)) may be used to manage the growth of the log files - once a log volume is closed, that file may be archived without ill- effect on the continued operation of ppppmmmmllllooooggggggggeeeerrrr. See also the ----vvvv option above. The buffers for the current log may be flushed to disk using the fffflllluuuusssshhhh command of ppppmmmmllllcccc(1), or by sending ppppmmmmllllooooggggggggeeeerrrr a SIGUSR1 signal. This is useful when the log needs to be read while ppppmmmmllllooooggggggggeeeerrrr is still running. When launched with the ----xxxx option, pmlogger will accept asynchronous control requests on the file descriptor _f_d. This option is only expected to be used internally by PCP applications that support ``live record mode'' via ppppmmmmRRRReeeeccccoooorrrrddddCCCCoooonnnnttttrrrroooollll(3). PPPPaaaaggggeeee 3333 PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRAAAATTTTIIIIOOOONNNN FFFFIIIILLLLEEEE SSSSYYYYNNNNTTTTAAAAXXXX The configuration file may be specified with the ----cccc option. If it is not, configuration specifications are read from standard input. If _c_o_n_f_i_g_f_i_l_e does not exist, then a search is made in the directory $_P_C_P__V_A_R__D_I_R/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r for a file of the same name, and if found that file is used, e.g. if _c_o_n_f_i_g._m_u_m_b_l_e does not exist in the current directory and the file $_P_C_P__V_A_R__D_I_R/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r/_c_o_n_f_i_g._m_u_m_b_l_e does exist, then ----cccc ccccoooonnnnffffiiiigggg....mmmmuuuummmmbbbblllleeee and ----cccc $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ccccoooonnnnffffiiiigggg////ppppmmmmllllooooggggggggeeeerrrr////ccccoooonnnnffffiiiigggg....mmmmuuuummmmbbbblllleeee are equivalent. The syntax for the configuration file is as follows. 1. Words are separated by white space (space, tab or newline). 2. The symbol ``#'' (hash) introduces a comment, and all text up to the next newline is ignored. 3. Keywords (shown in bbbboooolllldddd below) must appear literally (i.e. in lower case). 4. Each specification begins with the optional keyword lllloooogggg, followed by one of the states mmmmaaaannnnddddaaaattttoooorrrryyyy oooonnnn, mmmmaaaannnnddddaaaattttoooorrrryyyy ooooffffffff, mmmmaaaannnnddddaaaattttoooorrrryyyy mmmmaaaayyyybbbbeeee, aaaaddddvvvviiiissssoooorrrryyyy oooonnnn or aaaaddddvvvviiiissssoooorrrryyyy ooooffffffff. 5. For the oooonnnn states, a logging interval must follow using the syntax ``oooonnnncccceeee'', or ``ddddeeeeffffaaaauuuulllltttt'', or ``eeeevvvveeeerrrryyyy _N _t_i_m_e_u_n_i_t_s'', or simply ``_N _t_i_m_e_u_n_i_t_s'' - _N is an unsigned integer, and _t_i_m_e_u_n_i_t_s is one of the keywords mmmmsssseeeecccc, mmmmiiiilllllllliiiisssseeeeccccoooonnnndddd, sssseeeecccc, sssseeeeccccoooonnnndddd, mmmmiiiinnnn, mmmmiiiinnnnuuuutttteeee, hhhhoooouuuurrrr or the plural form of one of the above. Internal limitations require the interval to be smaller than (approximately) 74 hours. An interval value of zero is a synonym for oooonnnncccceeee. An interval of ddddeeeeffffaaaauuuulllltttt means to use the default logging interval of 60 seconds; this default value may be changed to _i_n_t_e_r_v_a_l with the ----tttt command line option. The _i_n_t_e_r_v_a_l argument follows the syntax described in PPPPCCCCPPPPIIIInnnnttttrrrroooo(1), and in the simplest form may be an unsigned integer (the implied units in this case are seconds). 6. Following the state and possible interval specifications comes a ``{'', followed by a list of one or more metric specifications and a closing ``}''. The list is white space (or comma) separated. If there is only one metric specification in the list, the braces are optional. 7. A metric specification consists of a metric name optionally followed by a set of instance names. The metric name follows the standard PCP naming conventions, see ppppmmmmnnnnssss(4), and if the metric name is a non-leaf node in the PMNS (see ppppmmmmnnnnssss(4)), then ppppmmmmllllooooggggggggeeeerrrr will recursively descend the PMNS and apply the logging specification to PPPPaaaaggggeeee 4444 PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) all descendent metric names that are leaf nodes in the PMNS. The set of instance names is a ``['', followed by a list of one or more space (or comma) separated names, numbers or strings, and a closing ``]''. Elements in the list that are numbers are assumed to be internal instance identifiers, other elements are assumed to be external instance identifiers - see ppppmmmmGGGGeeeettttIIIInnnnDDDDoooommmm(3) for more information. If no instances are given, then the logging specification is applied to all instances of the associated metric. 8. There may be an arbitrary number of logging specifications. 9. Following all of the logging specifications, there may be an optional access control section, introduced by the literal token [[[[aaaacccccccceeeessssssss]]]]. Thereafter come access control rules of the form ``aaaalllllllloooowwww _h_o_s_t_l_i_s_t :::: _o_p_e_r_a_t_i_o_n ;;;;'' and ``ddddiiiissssaaaalllllllloooowwww _h_o_s_t_l_i_s_t :::: _o_p_e_r_a_t_i_o_n ;;;;''. The base _o_p_e_r_a_t_i_o_n_s are aaaaddddvvvviiiissssoooorrrryyyy, mmmmaaaannnnddddaaaattttoooorrrryyyy and eeeennnnqqqquuuuiiiirrrreeee. In all other aspects, these access control statements follow the syntactic and semantic rules defined for the access control mechanisms used by PMCD and are fully documented in ppppmmmmccccdddd(1). EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS For each PCP utility, there is a sample ppppmmmmllllooooggggggggeeeerrrr configuration file that could be used to create an archive log suitable for replaying with that tool (i.e. includes all of the performance metrics used by the tool). For a tool named _f_o_o this configuration file is located in $_P_C_P__V_A_R__D_I_R/_c_o_n_f_i_g/_p_m_l_o_g_g_e_r/_c_o_n_f_i_g._f_o_o. The following is a simple default configuration file for a primary ppppmmmmllllooooggggggggeeeerrrr instance, and demonstrates most of the capabilities of the configuration specification language. log mandatory on once { hinv.ncpu hinv.ndisk } log mandatory on every 10 minutes { disk.all.write disk.all.read network.interface.in.packets [ "et0" ] network.interface.out.packets [ "et0" ] nfs.server.reqs [ "lookup" "getattr" "read" "write" ] } log advisory on every 30 minutes { environ.temp pmcd.pdu_in.total pmcd.pdu_out.total } [access] disallow * : all except enquire; allow localhost : mandatory, advisory; PPPPaaaaggggeeee 5555 PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) AAAAUUUUTTTTOOOOMMMMAAAATTTTIIIICCCC RRRREEEESSSSTTTTAAAARRRRTTTT It is often useful for ppppmmmmllllooooggggggggeeeerrrr processes (other than the primary instance) to be started and stopped when the local host is booted or shutdown. The script $_P_C_P__R_C__D_I_R/_p_c_p_l_o_c_a_l and the necessary soft-links are provided, and can be modified by rrrrooooooootttt to run PCP tools automatically. If you want to find out more before starting, read the manual pages for rrrrcccc2222(1), rrrrcccc0000(1), sssshhhhuuuuttttddddoooowwwwnnnn(1) and the file /_e_t_c/_i_n_i_t._d/_R_E_A_D_M_E. For example, changing $_P_C_P__R_C__D_I_R/_p_c_p_l_o_c_a_l so that it contains: # Add startup actions here ($PCP_BINADM_DIR/pmlogger_check &) ;; # Add shutdown actions here killall -INT pmlogger ;; will start ppppmmmmllllooooggggggggeeeerrrr instances at boot time and terminate them in an orderly fashion at system shutdown. This script runs as rrrrooooooootttt, so any _p_m_l_o_g_g_e_r instances it launches are also run as rrrrooooooootttt. To run some ppppmmmmllllooooggggggggeeeerrrr instances as a particular user, create your own archive logger control file (see ppppmmmmllllooooggggggggeeeerrrr____cccchhhheeeecccckkkk(1)) and use the ssssuuuu(1) command. e.g. # Add startup actions here (su tanya -c "$PCP_BINADM_DIR/pmlogger_check -c /usr/people/tanya/ctl" &) ;; at boot time will start the ppppmmmmllllooooggggggggeeeerrrr instances described in /_u_s_r/_p_e_o_p_l_e/_t_a_n_y_a/_c_t_l, running as user ttttaaaannnnyyyyaaaa. FFFFIIIILLLLEEEESSSS _a_r_c_h_i_v_e....mmmmeeeettttaaaa metadata (metric descriptions, instance domains, etc.) for the archive log _a_r_c_h_i_v_e....0000 initial volume of metrics values (subsequent volumes have suffixes 1111, 2222, ...) _a_r_c_h_i_v_e....iiiinnnnddddeeeexxxx temporal index to support rapid random access to the other files in the archive log $$$$PPPPCCCCPPPP____TTTTMMMMPPPP____DDDDIIIIRRRR////ppppmmmmllllooooggggggggeeeerrrr ppppmmmmllllooooggggggggeeeerrrr maintains the files in this directory as the map between the process id of the ppppmmmmllllooooggggggggeeeerrrr instance and the IPC port that may be used to control each ppppmmmmllllooooggggggggeeeerrrr instance (as used by ppppmmmmllllcccc(1)) ////eeeettttcccc////ccccoooonnnnffffiiiigggg////ppppmmmmllllooooggggggggeeeerrrr cccchhhhkkkkccccoooonnnnffffiiiigggg(1M) control flag, to control launching of ppppmmmmllllooooggggggggeeeerrrr from $$$$PPPPCCCCPPPP____RRRRCCCC____DDDDIIIIRRRR////ppppccccpppp ////eeeettttcccc////ccccoooonnnnffffiiiigggg////ppppmmmmllllooooggggggggeeeerrrr....ooooppppttttiiiioooonnnnssss command line options to ppppmmmmllllooooggggggggeeeerrrr when launched from $$$$PPPPCCCCPPPP____RRRRCCCC____DDDDIIIIRRRR////ppppccccpppp PPPPaaaaggggeeee 6666 PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ccccoooonnnnffffiiiigggg////ppppmmmmllllooooggggggggeeeerrrr////ccccoooonnnnffffiiiigggg....ddddeeeeffffaaaauuuulllltttt default configuration file for the primary logger instance launched from $$$$PPPPCCCCPPPP____RRRRCCCC____DDDDIIIIRRRR////ppppccccpppp $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ccccoooonnnnffffiiiigggg////ppppmmmmllllooooggggggggeeeerrrr////ccccoooonnnnffffiiiigggg....* assorted configuration files suitable for creating logs that may be subsequently replayed with the PCP visualization and monitoring tools $$$$PPPPCCCCPPPP____LLLLOOOOGGGG____DDDDIIIIRRRR////_h_o_s_t_n_a_m_e Default directory for PCP archive files for performance metric values collected from the host _h_o_s_t_n_a_m_e. ./_p_m_l_o_g_g_e_r._l_o_g (or $$$${{{{PPPPCCCCPPPP____LLLLOOOOGGGGDDDDIIIIRRRR----$$$$PPPPCCCCPPPP____LLLLOOOOGGGG____DDDDIIIIRRRR}}}}////_h_o_s_t_n_a_m_e////ppppmmmmllllooooggggggggeeeerrrr....lllloooogggg when started automatically by either $$$$PPPPCCCCPPPP____RRRRCCCC____DDDDIIIIRRRR////ppppccccpppp or one of the ppppmmmmllllooooggggggggeeeerrrr(1) monitoring scripts such as ppppmmmmllllooooggggggggeeeerrrr____cccchhhheeeecccckkkk(1)) all messages and diagnostics are directed here $$$$PPPPCCCCPPPP____RRRRCCCC____DDDDIIIIRRRR////ppppccccppppllllooooccccaaaallll contains ``hooks'' to enable automatic restart at system boot time EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT Normally ppppmmmmllllooooggggggggeeeerrrr creates a socket to receive control messages from ppppmmmmllllcccc(1) on the first available TCP/IP port numbered 4330 or higher. The environment variable PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR____PPPPOOOORRRRTTTT may be used to specify an alternative starting port number. PPPPCCCCPPPP EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT Environment variables with the prefix PPPPCCCCPPPP____ are used to parameterize the file and directory names used by PCP. On each installation, the file /_e_t_c/_p_c_p._c_o_n_f contains the local values for these variables. The $$$$PPPPCCCCPPPP____CCCCOOOONNNNFFFF variable may be used to specify an alternative configuration file, as described in ppppccccpppp....ccccoooonnnnffff(4). SSSSEEEEEEEE AAAALLLLSSSSOOOO PPPPCCCCPPPPIIIInnnnttttrrrroooo(1), ppppmmmmccccdddd(1), ppppmmmmdddduuuummmmpppplllloooogggg(1), ppppmmmmllllcccc(1), ppppmmmmllllooooggggggggeeeerrrr____cccchhhheeeecccckkkk(1), ppppccccpppp....ccccoooonnnnffff(4), ppppccccpppp....eeeennnnvvvv(4) and ppppmmmmnnnnssss(4). If you have the PCP product, relevant information is also available from the on-line PCP Tutorial. Provided the ppppccccpppp....mmmmaaaannnn....ttttuuuuttttoooorrrriiiiaaaallll subsystem from the PCP images has been installed, access the URL ffffiiiilllleeee::::$$$$PPPPCCCCPPPP____DDDDOOOOCCCC____DDDDIIIIRRRR////TTTTuuuuttttoooorrrriiiiaaaallll////aaaarrrrcccchhhhiiiivvvveeee....hhhhttttmmmmllll from your web browser. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS The archive logs are sufficiently precious that ppppmmmmllllooooggggggggeeeerrrr will not truncate an existing physical file. A message of the form __pmLogNewFile: "foo.index" already exists, not over-written __pmLogCreate: File exists indicates this situation has arisen. You must explicitly remove the files and launch ppppmmmmllllooooggggggggeeeerrrr again. PPPPaaaaggggeeee 7777 PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR((((1111)))) There may be at most one primary ppppmmmmllllooooggggggggeeeerrrr instance per monitored host; attempting to bend this rule produces the error: pmlogger: there is already a primary pmlogger running Various other messages relating to the creation and/or deletion of files in $_P_C_P__T_M_P__D_I_R/_p_m_l_o_g_g_e_r suggest a permission problem on this directory, or some feral files have appeared therein. PPPPaaaaggggeeee 8888 
